Skip to content

docs(ams): recommend API-key credentials for unattended coding-agent setup - #6854

Merged
JSONbored merged 1 commit into
mainfrom
docs/ams-credential-decision-6845
Jul 17, 2026
Merged

docs(ams): recommend API-key credentials for unattended coding-agent setup#6854
JSONbored merged 1 commit into
mainfrom
docs/ams-credential-decision-6845

Conversation

@JSONbored

@JSONbored JSONbored commented Jul 17, 2026

Copy link
Copy Markdown
Owner

Summary

Design/research deliverable for #6845 (part of epic #6844). Surveys claude-cli's and codex-cli's real, verified credential mechanisms and recommends a concrete default for init --interactive per deployment context.

Closes #6845

Recommendation

Default to a provider API key (ANTHROPIC_API_KEY / OPENAI_API_KEY) for no-TTY/fleet/server contexts, keeping the current subscription-backed device-flow OAuth (claude setup-token / codex login --device-auth) as the offered default only in a real interactive session. Both already work today — this is a default/ordering recommendation, not a new capability. Full reasoning and verification evidence in the doc.

This is a non-binding recommendation only; the actual wizard behavior change is #6846, which depends on this issue.

Test plan

  • npm run docs:drift-check
  • npm run test:miner-deployment-docs-audit

@JSONbored
docs(ams): recommend API-key credentials for unattended coding-agent …
87dc378 
…setup

Surveys claude-cli's and codex-cli's real credential mechanisms
(subscription-backed device-flow OAuth vs a plain provider API key)
and recommends defaulting init --interactive to the API-key path for
no-TTY/fleet/server contexts, keeping the OAuth path for interactive
laptop use where a human already pays for a subscription plan.

Non-binding design input for #6846's wizard implementation.

Closes #6845
@JSONbored JSONbored self-assigned this Jul 17, 2026
@JSONbored
JSONbored marked this pull request as draft July 17, 2026 08:38
@loopover-orb loopover-orb Bot added the gittensor:feature Gittensor-scored feature linked to a feature issue — scores a 0.25x multiplier. label Jul 17, 2026
@loopover-orb

loopover-orb Bot commented Jul 17, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Warning

⏸️ LoopOver review result - manual review recommended

Review updated: 2026-07-17 08:39:49 UTC

1 file · no blockers · CI pending · blocked

⏸️ Suggested Action - Manual Review

Nits — 2 non-blocking
  • PR author also opened the linked issue — Link an issue that was opened by a different contributor, or provide a rationale for why this self-authored issue represents genuine discovery work.
  • Diff looks like trivial or whitespace-only churn — Reduce whitespace-only or formatting-only churn and keep the diff focused on substantive changes.

Decision drivers

  • ✅ Code review — No blockers (No AI review summary)
  • ✅ Gate result — Passing (No configured blocker found.)
Context & advisory signals — never blocks the verdict
Signal Result Evidence
Linked issue ✅ Linked #6845
Related work ✅ No active overlap found No same-issue or scoped active PR overlap found.
Change scope ❌ 8/20 High review scope from cached public metadata (draft PR; 1 linked issue).
Validation posture ✅ 25/25 PR body includes validation/test evidence.
Contributor workload ✅ 10/10 Author activity: 33 registered-repo PR(s), 26 merged, 332 issue(s).
Contributor context ✅ Confirmed Gittensor contributor JSONbored; Gittensor profile; 33 PR(s), 332 issue(s).
Improvement ℹ️ Insufficient signal risk: low · value: insufficient-signal
Review context
  • Author: JSONbored
  • Role context: owner (maintainer lane)
  • Public audience mode: oss maintainer
  • Lane context: Repository is configured for direct PR review.
  • Public profile languages: Python, TypeScript, Ruby, Go, JavaScript, MDX, Shell, Solidity
  • Official Gittensor activity: 33 PR(s), 332 issue(s).
  • PR-specific overlap: none found.
Contributor next steps
  • Start here: Treat this as maintainer-lane context rather than normal contributor-lane activity.
  • Then work through the remaining 3 steps in the Signals table above.
Signal definitions
  • Related work = same linked issue, overlapping active PRs, or title/path similarity.
  • Change scope = cached public metadata such as size labels, draft state, and review-burden hints.
  • Validation posture = whether the PR provides enough public validation/test evidence for maintainer review.
  • Contributor workload = public contributor activity and cleanup pressure, not a repo-wide quality failure.
  • Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.
🧪 Chat with LoopOver

Ask LoopOver a question about this PR directly in a comment — grounded only in the same cached, public-safe facts shown above, never a new claim.

  • @loopover ask <question> answers contribution-quality Q&A with source citations and freshness.
  • @loopover chat <question> answers in natural prose from cached decision-pack facts via local inference (maintainer/collaborator; read-only).
  • A plain-language @loopover mention with a real question is routed to the closest matching read-only command automatically — no exact syntax required.

Full command reference: https://loopover.ai/docs/loopover-commands

🧪 Experimental — new and may change.

🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed

💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

Checked by LoopOver, a quiet PR intelligence layer for OSS maintainers.

  • Re-run LoopOver review

@superagent-security

superagent-security Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Superagent didn't find any vulnerabilities or security issues in this PR.

@JSONbored
JSONbored marked this pull request as ready for review July 17, 2026 08:45
@JSONbored
JSONbored merged commit df78a7c into main Jul 17, 2026
14 checks passed
@JSONbored
JSONbored deleted the docs/ams-credential-decision-6845 branch July 17, 2026 08:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@JSONbored JSONbored

Labels

gittensor:feature Gittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

AMS credentials: decide the recommended default (subscription OAuth vs API key) for claude-cli and codex-cli

1 participant

@JSONbored